\subsection{Choice of Use Case}
Out of the four use cases that were presented , interest was shown in three. After discussion and voting, Flight Routing Use Case was selected as it presented a simple and easy accessible domain allowing for much functionality.\\

\subsection{Case abstract of Flight Routing}
The case abstract of the flight route is as follows:

\begin{quotation}
Using a distributed platform with a web or mobile interface, you are to develop a flight routing system based on flight routing data put at your disposal. The objective is to make a minimum-cost-estimated route from flight departure to flight destination with intermediate legs in the route.\\
\end{quotation}


%Nødvendigt afsnit?

%\subsection{Flight Routing System content expectations}
%    Algorithms: Shortest path, best and worst running time, graph and data structure theory. \\
%    Concurrency: Booking seats, ensuring mutual exclusion and the ACID properties through locking seats, local/host update. %\\
%    Client application: An application made in WPF or Windows forms using a MVC backend through a WCF service layer. \\ 
%    Web: A separate web application written in a mix of html, css, JavaScript, asp.NET. \\
%    Pre conditions: user profile is created, a standard user with login. \\ \\
%    We expect to create a client application for ticket and seat booking to be used at the airport and a web application %for ticket booking alone. 
%    We expect the project to have special focus on algorithms for finding the optimal route with the best possible running %time and graphs to become useful for this purpose. As well we expect concurrency to come into play in the sense that a seat %booking has to be taken care of; in order to make sure that a seat can only be booked by one user at a time.